User avatar mt:weblate-translation-memory

Suggestion added

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
Follow xref:Installing_Packager_Tools.adoc[Installing Packager Tools].
Siga xref:Installing_Packager_Tools.adoc[Instalar Herramientas de Empaquetador].
2 months ago
User avatar mt:weblate-translation-memory

Suggestion added

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
Install Packager Tools
Instalar Herramientas de Empaquetador
2 months ago
User avatar None

Changes pushed

  1. fedora-docs-l10n/package-maintainers
  2. nav
Changes pushed 2 months ago
User avatar None

Repository notification received

  1. fedora-docs-l10n/package-maintainers
  2. nav
Pagure: https://pagure.io/fedora-docs-l10n/package-maintainers, master 2 months ago
User avatar vareli

Resource updated

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
File “po/es/master/pages/New_Package_Process_for_New_Contributors.po” was added. 2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
Fedora has the infrastructure available for monitoring new upstream releases of the software you are packaging. Refer to xref:Upstream_Release_Monitoring.adoc[Upstream Release Monitoring] for more details.
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
Watch for updates
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
[#watch_for_updates]
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
If appropriate for the package, make it available in "comps" files so that it can be selected during installation and included in dnf package group operations. See https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups?rd=PackageMaintainers/CompsXml[How to use and edit comps.xml for package groups] for more info.
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
Make the package available in "comps" files
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
[#make_the_package_available_in_comps_files]
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
Please see the xref:Package_Update_Guide.adoc[Package Update Guide] for more details.
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
You can also select multiple builds from different packages
to include in a single update using the web interface.
This is useful when you would like to push linked builds,
for example: an application package and its dependencies
that are necessary for it to run correctly.
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
It is often easier to complete builds for all your branches
and then push a single update using the https://bodhi.fedoraproject.org/updates/new[Bodhi web interface].
Bodhi is smart enough to split your update into individual updates,
one for each Fedora release branch.
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
fedpkg update
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
You can push an update using Bodhi via the command line using this in each branch:
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
The Fedora update system called https://bodhi.fedoraproject.org[Bodhi] is used for pushing updates, classifying packages etc. You do not need to submit updates for Rawhide (main) manually because these are automatically created for you when the build completes. For all other branches, you must manually push updates for all builds that you would like to make available to users.
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
Submit Package as Update in Bodhi
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
[#submit_package_as_update_in_bodhi]
 
2 months ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/New_Package_Process_for_New_Contributors
  3. Spanish
If it fails to build,
the build system will send you an email
to report the failure
and show you to the logs.
Commit any needed changes to git,
bump the SPEC release number,
and request a new build.
 
2 months ago

Search